Skip to content

Conversation

@LittleBeannie
Copy link
Collaborator

To solve issue #520.

@LittleBeannie LittleBeannie self-assigned this Aug 25, 2025
@LittleBeannie LittleBeannie linked an issue Aug 25, 2025 that may be closed by this pull request
@LittleBeannie LittleBeannie marked this pull request as draft August 25, 2025 20:39
@LittleBeannie LittleBeannie marked this pull request as ready for review August 26, 2025 19:20
Merge branch 'main' into 520-improve-the-help-file-of-gs_power_npe-and-gs_design_npe

# Conflicts:
#	R/gs_design_npe.R
#	R/gs_power_npe.R
#	man/gs_design_npe.Rd
#	man/gs_power_npe.Rd
@LittleBeannie LittleBeannie requested a review from keaven September 5, 2025 18:37
Copy link
Collaborator

@keaven keaven left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested Documentation Improvements for gs_power_npe.R from CoPilot:

Title, Description, and Overview
Change “allows” to “allow” in:

The following 2 functions allows a non-constant treatment effect over time
Correction:
The following two functions allow a non-constant treatment effect over time

Change “They requires” to “They require”

They requires treatment effect and statistical information at each analysis
Correction:
They require treatment effect and statistical information at each analysis

Remove comma before “and” in:

Initial bound types supported are spending bounds, and fixed bounds.
Correction:
Initial bound types supported are spending bounds and fixed bounds.

Use “These routines” instead of “The above routine” for clarity and flow.

Function Descriptions
Use “and the method for deriving bounds” instead of “as well as the method of deriving bounds.”
Clarify the difference between the two functions:
The only differences in arguments of the 2 functions are the \code{alpha} and \code{beta} used in the \code{gs_design_npe()}.
Correction:
The only differences in arguments between the two functions are the \code{alpha} and \code{beta} parameters, which are used in \code{gs_design_npe()}.

Parameters
Change “Users are required to provide the value of theta.” to

The user must provide a value for theta.

Change “Default is 0. If users provide values other than 0, it impacts upper bound computation.” to

The default is 0. If a value other than 0 is provided, it affects upper bound computation.

Change “It is a vector of all positive numbers with increasing order.” to

It is a vector of positive numbers in increasing order.

Change “Users are required to input it corresponding to theta.” to

The user must provide values corresponding to theta.

Return Value
Change “the info, info0, info1 is same as the input.” to

the info, info0, and info1 are the same as the input.

Change “the info, info0, info1 is change by some constant scale factor…” to

the info, info0, and info1 are changed by a constant scale factor…

Examples
Ensure comments start with a capital letter and reference functions in backticks for clarity.
Example:
Default of gs_power_npe (single analysis; Type I error controlled)
Correction:
Default of gs_power_npe (single analysis; Type I error controlled)
General Suggestions:

Use present tense for function capabilities.
Make sentences complete and clear.
Avoid ambiguous references like "the above routine"—use "this routine" or "these routines."
Standardize bullet points and formatting.

@LittleBeannie
Copy link
Collaborator Author

Suggested Documentation Improvements for gs_power_npe.R from CoPilot:

Title, Description, and Overview Change “allows” to “allow” in:

The following 2 functions allows a non-constant treatment effect over time Correction: The following two functions allow a non-constant treatment effect over time

Change “They requires” to “They require”

They requires treatment effect and statistical information at each analysis Correction: They require treatment effect and statistical information at each analysis

Remove comma before “and” in:

Initial bound types supported are spending bounds, and fixed bounds. Correction: Initial bound types supported are spending bounds and fixed bounds.

Use “These routines” instead of “The above routine” for clarity and flow.

Function Descriptions Use “and the method for deriving bounds” instead of “as well as the method of deriving bounds.” Clarify the difference between the two functions: The only differences in arguments of the 2 functions are the \code{alpha} and \code{beta} used in the \code{gs_design_npe()}. Correction: The only differences in arguments between the two functions are the \code{alpha} and \code{beta} parameters, which are used in \code{gs_design_npe()}.

Parameters Change “Users are required to provide the value of theta.” to

The user must provide a value for theta.

Change “Default is 0. If users provide values other than 0, it impacts upper bound computation.” to

The default is 0. If a value other than 0 is provided, it affects upper bound computation.

Change “It is a vector of all positive numbers with increasing order.” to

It is a vector of positive numbers in increasing order.

Change “Users are required to input it corresponding to theta.” to

The user must provide values corresponding to theta.

Return Value Change “the info, info0, info1 is same as the input.” to

the info, info0, and info1 are the same as the input.

Change “the info, info0, info1 is change by some constant scale factor…” to

the info, info0, and info1 are changed by a constant scale factor…

Examples Ensure comments start with a capital letter and reference functions in backticks for clarity. Example: Default of gs_power_npe (single analysis; Type I error controlled) Correction: Default of gs_power_npe (single analysis; Type I error controlled) General Suggestions:

Use present tense for function capabilities. Make sentences complete and clear. Avoid ambiguous references like "the above routine"—use "this routine" or "these routines." Standardize bullet points and formatting.

The above comments are addressed in the latest commit, and I will merge this PR.

@LittleBeannie LittleBeannie merged commit 325f54a into main Sep 9, 2025
7 checks passed
@LittleBeannie LittleBeannie deleted the 520-improve-the-help-file-of-gs_power_npe-and-gs_design_npe branch September 9, 2025 17:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Improve the help file of gs_power_npe and gs_design_npe

4 participants